Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e998d0bb94d1ce42c235fa14381d97df94cf8699b2a46c394fb0738110780952

Tx prefix hash: 590bb73844afbc1850cac903f6b64885be1430f7996ea00c3e65633dcf74c51e
Tx public key: 4d2c8a642a2b2dbeb602714b2961f93f2674617e2dee0f4dc1d6d2eb7cf6cd44
Timestamp: 1716941094 Timestamp [UCT]: 2024-05-29 00:04:54 Age [y:d:h:m:s]: 01:021:08:53:08
Block: 1032201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276042 RingCT/type: yes/0
Extra: 014d2c8a642a2b2dbeb602714b2961f93f2674617e2dee0f4dc1d6d2eb7cf6cd44021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de5c4ce1130e4838f5de45294a82b6b3dad66fa82a67e57e20264a2899441355 0.600000000000 1500650 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": 1032211, "vin": [ { "gen": { "height": 1032201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de5c4ce1130e4838f5de45294a82b6b3dad66fa82a67e57e20264a2899441355" } } ], "extra": [ 1, 77, 44, 138, 100, 42, 43, 45, 190, 182, 2, 113, 75, 41, 97, 249, 63, 38, 116, 97, 126, 45, 238, 15, 77, 193, 214, 210, 235, 124, 246, 205, 68, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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