Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d19e62aff968cc0de4209019a26b3fcf27095591ddf2c314c77c8568a49817

Tx prefix hash: 0b6997b8a18e96f0a3f897ba2bde9fb12294b28edb076c02a3af285bafee7a6a
Tx public key: 068c53fc7a3ceb007c634c980d2d2a402ebe5b44afc41ca626b1dfcfc5b7838e
Timestamp: 1726198373 Timestamp [UCT]: 2024-09-13 03:32:53 Age [y:d:h:m:s]: 00:199:16:16:58
Block: 1108932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142548 RingCT/type: yes/0
Extra: 01068c53fc7a3ceb007c634c980d2d2a402ebe5b44afc41ca626b1dfcfc5b7838e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0639b4a5861715ca0ca2dd778bf31a7db154d3c77b7bed8f8643985a431d4d22 0.600000000000 1587011 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": 1108942, "vin": [ { "gen": { "height": 1108932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0639b4a5861715ca0ca2dd778bf31a7db154d3c77b7bed8f8643985a431d4d22" } } ], "extra": [ 1, 6, 140, 83, 252, 122, 60, 235, 0, 124, 99, 76, 152, 13, 45, 42, 64, 46, 190, 91, 68, 175, 196, 28, 166, 38, 177, 223, 207, 197, 183, 131, 142, 2, 17, 0, 0, 0, 4, 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