Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e538420c8c8e1c75d65247ec39f2d712c1d2f07a41b78c5d2857832c3d86d7f0

Tx prefix hash: 9e139a4cce6a5272530a4b43f98685bbdfcb8da132097f91d631bce0893c11a3
Tx public key: 36256b471a2b509791e1ce004aae8f294f26df5cd2e703b2007670b06669ee63
Timestamp: 1727738117 Timestamp [UCT]: 2024-09-30 23:15:17 Age [y:d:h:m:s]: 00:054:08:27:16
Block: 1121708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38838 RingCT/type: yes/0
Extra: 0136256b471a2b509791e1ce004aae8f294f26df5cd2e703b2007670b06669ee63021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 339e521e1a03cee6a2af87c411dd1590877f6f1b446be541bece2545a6021f5a 0.600000000000 1604029 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": 1121718, "vin": [ { "gen": { "height": 1121708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "339e521e1a03cee6a2af87c411dd1590877f6f1b446be541bece2545a6021f5a" } } ], "extra": [ 1, 54, 37, 107, 71, 26, 43, 80, 151, 145, 225, 206, 0, 74, 174, 143, 41, 79, 38, 223, 92, 210, 231, 3, 178, 0, 118, 112, 176, 102, 105, 238, 99, 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