Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd975e4897e3d376b9c1de07ecae25c26767c6f4892c63f03b15253184262bfd

Tx prefix hash: f77a55a63815f012c8b239525b4f5e191d075a65ef43858ffbd7df8725b9f637
Tx public key: 10d4a680032e0d39dc127d84fc0b2a5837a59e725180ef2ac37af66f1a972bd3
Timestamp: 1730810241 Timestamp [UCT]: 2024-11-05 12:37:21 Age [y:d:h:m:s]: 00:078:05:36:39
Block: 1147081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55944 RingCT/type: yes/0
Extra: 0110d4a680032e0d39dc127d84fc0b2a5837a59e725180ef2ac37af66f1a972bd3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 495756435fd0c4072e0e02ddd48b35d1c5d6238770cbcbd3c10afd8087c96739 0.600000000000 1631774 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": 1147091, "vin": [ { "gen": { "height": 1147081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "495756435fd0c4072e0e02ddd48b35d1c5d6238770cbcbd3c10afd8087c96739" } } ], "extra": [ 1, 16, 212, 166, 128, 3, 46, 13, 57, 220, 18, 125, 132, 252, 11, 42, 88, 55, 165, 158, 114, 81, 128, 239, 42, 195, 122, 246, 111, 26, 151, 43, 211, 2, 17, 0, 0, 0, 5, 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