Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1280dcc1108cd1caf751df16b8f35becacf6c02bd9feb441f80878aed9b47d90

Tx prefix hash: f11b8e1421be3098b2310771d7209421412cde5347e344b542a314d6a8789d55
Tx public key: 71f098b008957e2ceef2e26d4218324a093c746d9a57effeb1397536b8a4a701
Timestamp: 1706588478 Timestamp [UCT]: 2024-01-30 04:21:18 Age [y:d:h:m:s]: 01:092:02:17:41
Block: 946345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326909 RingCT/type: yes/0
Extra: 0171f098b008957e2ceef2e26d4218324a093c746d9a57effeb1397536b8a4a7010211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542d53b1b217b991725bb2e4d4221ce2c815d75d55a2c7155b1f006e2ea24789 0.600000000000 1404677 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 946355, "vin": [ { "gen": { "height": 946345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542d53b1b217b991725bb2e4d4221ce2c815d75d55a2c7155b1f006e2ea24789" } } ], "extra": [ 1, 113, 240, 152, 176, 8, 149, 126, 44, 238, 242, 226, 109, 66, 24, 50, 74, 9, 60, 116, 109, 154, 87, 239, 254, 177, 57, 117, 54, 184, 164, 167, 1, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8