Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc9aed75835a141029aee20ac0f3d479a0692fdbe32f4e9722af766a940f941

Tx prefix hash: 61d8d196ed6412378cff0425b19bccbbe9bd9ab33d8de997cb8cab807482dc0f
Tx public key: 2280cd3eb788084a6638c60b2c0d0d8630f2424a8956b299e6fb2e184cfbaa0d
Timestamp: 1686954575 Timestamp [UCT]: 2023-06-16 22:29:35 Age [y:d:h:m:s]: 01:330:17:34:15
Block: 783834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497577 RingCT/type: yes/0
Extra: 012280cd3eb788084a6638c60b2c0d0d8630f2424a8956b299e6fb2e184cfbaa0d021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.551789206000 dcy

stealth address amount amount idx
00: 2f6906ecf2d3600a37648b8bc0fff62d8b5e8b13a04fc36b3be17a72aa49d44e 1.551789206000 1233705 of 0

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": 783844, "vin": [ { "gen": { "height": 783834 } } ], "vout": [ { "amount": 1551789206, "target": { "key": "2f6906ecf2d3600a37648b8bc0fff62d8b5e8b13a04fc36b3be17a72aa49d44e" } } ], "extra": [ 1, 34, 128, 205, 62, 183, 136, 8, 74, 102, 56, 198, 11, 44, 13, 13, 134, 48, 242, 66, 74, 137, 86, 178, 153, 230, 251, 46, 24, 76, 251, 170, 13, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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