Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12cdcf55a60afb58927fbeefc1373ddd60c182f397ff6b35fa59b72e602787b

Tx prefix hash: 1c5a9a0ff76d0dafa9d79ec6e9ea68b23e9b51ac96e44a426a90279288e3f326
Tx public key: 2f8804d11f18f39d993b7557cb4a898777a08d04137468d20bdbce56f89003b9
Timestamp: 1735670024 Timestamp [UCT]: 2024-12-31 18:33:44 Age [y:d:h:m:s]: 00:322:04:37:50
Block: 1187333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227791 RingCT/type: yes/0
Extra: 012f8804d11f18f39d993b7557cb4a898777a08d04137468d20bdbce56f89003b9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ce415cd8ce6b77fd9079e3ea1902d7e26819df5b5f5b46707d9da9f6341d597 0.600000000000 1673822 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": 1187343, "vin": [ { "gen": { "height": 1187333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ce415cd8ce6b77fd9079e3ea1902d7e26819df5b5f5b46707d9da9f6341d597" } } ], "extra": [ 1, 47, 136, 4, 209, 31, 24, 243, 157, 153, 59, 117, 87, 203, 74, 137, 135, 119, 160, 141, 4, 19, 116, 104, 210, 11, 219, 206, 86, 248, 144, 3, 185, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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