Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf7c0b29bca6d701867ec10e4546fe3650725a653e10fb372f24cc0d977083a

Tx prefix hash: b34caa211fc925a4fd90e7c957483bb9179ac888ae3e32fba69c57b16762e260
Tx public key: cb1503c40d8fb37c5db1caf22e4bb10d8b54ba345ce6f9941e51bf9f99171bb9
Timestamp: 1698359165 Timestamp [UCT]: 2023-10-26 22:26:05 Age [y:d:h:m:s]: 01:163:00:20:21
Block: 878361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377483 RingCT/type: yes/0
Extra: 01cb1503c40d8fb37c5db1caf22e4bb10d8b54ba345ce6f9941e51bf9f99171bb9021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.754441200000 dcy

stealth address amount amount idx
00: 875b68212c8efcd54037af49635907be904527570a9f18e5637436f1ac7b82a5 0.754441200000 1333799 of 0

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": 878371, "vin": [ { "gen": { "height": 878361 } } ], "vout": [ { "amount": 754441200, "target": { "key": "875b68212c8efcd54037af49635907be904527570a9f18e5637436f1ac7b82a5" } } ], "extra": [ 1, 203, 21, 3, 196, 13, 143, 179, 124, 93, 177, 202, 242, 46, 75, 177, 13, 139, 84, 186, 52, 92, 230, 249, 148, 30, 81, 191, 159, 153, 23, 27, 185, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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