Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a4b6448b5636b104e51b0c6df47c8291dca46c3aa4330a3862093b3c722959

Tx prefix hash: 1669fe2ac481cefbeadeb55aa8327a4e713d72afdb1f80c5d58b7ea76687c491
Tx public key: 08644f4c8fa539943f0fe81309ebd637aaa4b9a68fbbe8d261fef57a525b1a09
Timestamp: 1736805696 Timestamp [UCT]: 2025-01-13 22:01:36 Age [y:d:h:m:s]: 00:158:15:44:47
Block: 1196736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113057 RingCT/type: yes/0
Extra: 0108644f4c8fa539943f0fe81309ebd637aaa4b9a68fbbe8d261fef57a525b1a09021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abdee5671aee04885efb12d4b9fa8cabb3710d80500ae393aa43b458a55b9219 0.600000000000 1683339 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": 1196746, "vin": [ { "gen": { "height": 1196736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abdee5671aee04885efb12d4b9fa8cabb3710d80500ae393aa43b458a55b9219" } } ], "extra": [ 1, 8, 100, 79, 76, 143, 165, 57, 148, 63, 15, 232, 19, 9, 235, 214, 55, 170, 164, 185, 166, 143, 187, 232, 210, 97, 254, 245, 122, 82, 91, 26, 9, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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