Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba9667a23e2c98e9f6f681a5666f3bbb56273fbd3fe93e49d857560048c1d859

Tx prefix hash: b5269351ac512108045b05c58c62cd2f8bc97382b03af290c0975f58e43f8b9d
Tx public key: 56e2c212b3b7d3d1fafeceac32682559904e3629b4b681886ac5531bfc9d072c
Timestamp: 1726675115 Timestamp [UCT]: 2024-09-18 15:58:35 Age [y:d:h:m:s]: 00:212:08:18:15
Block: 1112889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151607 RingCT/type: yes/0
Extra: 0156e2c212b3b7d3d1fafeceac32682559904e3629b4b681886ac5531bfc9d072c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba5514dd670e03f299e0eef0bb73ceeda4443d5f0c2122f5ba6aaec8a38b8541 0.600000000000 1592372 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": 1112899, "vin": [ { "gen": { "height": 1112889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba5514dd670e03f299e0eef0bb73ceeda4443d5f0c2122f5ba6aaec8a38b8541" } } ], "extra": [ 1, 86, 226, 194, 18, 179, 183, 211, 209, 250, 254, 206, 172, 50, 104, 37, 89, 144, 78, 54, 41, 180, 182, 129, 136, 106, 197, 83, 27, 252, 157, 7, 44, 2, 17, 0, 0, 0, 3, 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