Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 448946ffd6f78e214b8d5f79e2e02c450634f2c652ea642ea7b542ab5d46ba38

Tx prefix hash: 4eb43d4948610f0e774ac3736d71d2c3e57c6fcdd7ab3525ed9704af1c407ea0
Tx public key: dba8297dbd03920f8c7da1b0fe44ab3e5d1100f062c6fa673443da854fd3c322
Timestamp: 1726051614 Timestamp [UCT]: 2024-09-11 10:46:54 Age [y:d:h:m:s]: 01:073:00:26:29
Block: 1107730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310618 RingCT/type: yes/0
Extra: 01dba8297dbd03920f8c7da1b0fe44ab3e5d1100f062c6fa673443da854fd3c32202110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39888a6951f503b0888a5498f99077f9d3d0769e1ef926c3e015106ed0099d85 0.600000000000 1585371 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": 1107740, "vin": [ { "gen": { "height": 1107730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39888a6951f503b0888a5498f99077f9d3d0769e1ef926c3e015106ed0099d85" } } ], "extra": [ 1, 219, 168, 41, 125, 189, 3, 146, 15, 140, 125, 161, 176, 254, 68, 171, 62, 93, 17, 0, 240, 98, 198, 250, 103, 52, 67, 218, 133, 79, 211, 195, 34, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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