Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca062481d015b9785663c69e7fda77ed14da11fe80eadc3d62c93d2e903bb0c9

Tx prefix hash: fea86285be13bb88db2196377cca9a839b5b6f1e1ce0437b1b8946a6adb2c3bb
Tx public key: b0a0a9a32b194597cb55abb05bf834b0a5e1123e62889114275c2ffdf61f843d
Timestamp: 1723639675 Timestamp [UCT]: 2024-08-14 12:47:55 Age [y:d:h:m:s]: 00:147:20:23:25
Block: 1087738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105759 RingCT/type: yes/0
Extra: 01b0a0a9a32b194597cb55abb05bf834b0a5e1123e62889114275c2ffdf61f843d02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1517e89ceb756199eca38da1aebc7f32dcd2584af95cafa7a89d1b1d5e1bbcb 0.600000000000 1562349 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": 1087748, "vin": [ { "gen": { "height": 1087738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1517e89ceb756199eca38da1aebc7f32dcd2584af95cafa7a89d1b1d5e1bbcb" } } ], "extra": [ 1, 176, 160, 169, 163, 43, 25, 69, 151, 203, 85, 171, 176, 91, 248, 52, 176, 165, 225, 18, 62, 98, 136, 145, 20, 39, 92, 47, 253, 246, 31, 132, 61, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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