Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7abac2e1752201fb48f22bdde49a363f193c9dc9329cf8c6578c29ef138ee93c

Tx prefix hash: d098400b8d19932445f3bed30addcb129bc60ef9b1e366d9a4c259aae0e045cb
Tx public key: 4f0aa0d2a819218144fcc0a113ac2d7ffe96e8403f55b55bbb286d68187a16ce
Timestamp: 1714957627 Timestamp [UCT]: 2024-05-06 01:07:07 Age [y:d:h:m:s]: 00:316:00:09:52
Block: 1015751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225894 RingCT/type: yes/0
Extra: 014f0aa0d2a819218144fcc0a113ac2d7ffe96e8403f55b55bbb286d68187a16ce02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e06838df9acaf7d9aba1e5b11360875c61a04fd0840b4133f0dfa2798179e8fd 0.600000000000 1479192 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": 1015761, "vin": [ { "gen": { "height": 1015751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e06838df9acaf7d9aba1e5b11360875c61a04fd0840b4133f0dfa2798179e8fd" } } ], "extra": [ 1, 79, 10, 160, 210, 168, 25, 33, 129, 68, 252, 192, 161, 19, 172, 45, 127, 254, 150, 232, 64, 63, 85, 181, 91, 187, 40, 109, 104, 24, 122, 22, 206, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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