Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6d9e6b624098dcb27a0042ed5720f0574b6c91cb24bb47206a5a4a6b988b2bb

Tx prefix hash: 1d55b45dd6551ceb990497dfe85091f97f4f41b6d0b93c466a7f967f28c9f2e6
Tx public key: fc9e7e8e73fa4b8dd4fec5385c2086789c2774136e440701d4bc16fd76605e82
Timestamp: 1703371224 Timestamp [UCT]: 2023-12-23 22:40:24 Age [y:d:h:m:s]: 01:123:08:01:06
Block: 919688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349289 RingCT/type: yes/0
Extra: 01fc9e7e8e73fa4b8dd4fec5385c2086789c2774136e440701d4bc16fd76605e8202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d476cc5f0285ca3fc0a143f2c276ff8c5d75da5670e8f8a00ce71cdc1dbcfff 0.600000000000 1377364 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": 919698, "vin": [ { "gen": { "height": 919688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d476cc5f0285ca3fc0a143f2c276ff8c5d75da5670e8f8a00ce71cdc1dbcfff" } } ], "extra": [ 1, 252, 158, 126, 142, 115, 250, 75, 141, 212, 254, 197, 56, 92, 32, 134, 120, 156, 39, 116, 19, 110, 68, 7, 1, 212, 188, 22, 253, 118, 96, 94, 130, 2, 17, 0, 0, 0, 2, 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