Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc663e37278ee63c5bb006d369e23459d6c96643e99a99f94c0918620de73823

Tx prefix hash: b373ce51b15ef33bca4c70fb7d3ea3c3330f12867f7244ae0a61a35fa194245e
Tx public key: 0bb713f92604c9709c787971f7673d7e9cb8b3a1ee3f18e3639f760081e00c0f
Timestamp: 1729124313 Timestamp [UCT]: 2024-10-17 00:18:33 Age [y:d:h:m:s]: 00:148:18:46:16
Block: 1133203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106117 RingCT/type: yes/0
Extra: 010bb713f92604c9709c787971f7673d7e9cb8b3a1ee3f18e3639f760081e00c0f0211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29e9197204a5e83a516495d72af98673104ede65b053de6c63aa0c48028c61b5 0.600000000000 1616276 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": 1133213, "vin": [ { "gen": { "height": 1133203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29e9197204a5e83a516495d72af98673104ede65b053de6c63aa0c48028c61b5" } } ], "extra": [ 1, 11, 183, 19, 249, 38, 4, 201, 112, 156, 120, 121, 113, 247, 103, 61, 126, 156, 184, 179, 161, 238, 63, 24, 227, 99, 159, 118, 0, 129, 224, 12, 15, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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