Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09f7bde300f2965a8cfcd5de4e4f67b3551a48f275b1822b5841f660ce143b0b

Tx prefix hash: 4ba2c3a44c59f25a388145e602e9f45ccf82e9aff8736ccdf97074e24981b02c
Tx public key: b8173d28ae5dccb080d7c7028f00b49be79d3b5807bdf2413fcafa6504a5837b
Timestamp: 1724571335 Timestamp [UCT]: 2024-08-25 07:35:35 Age [y:d:h:m:s]: 00:220:19:39:41
Block: 1095453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157672 RingCT/type: yes/0
Extra: 01b8173d28ae5dccb080d7c7028f00b49be79d3b5807bdf2413fcafa6504a5837b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1757209384c34184df6a0e11bd60d6b7dc114b35a486a2ee09718d3386cf147 0.600000000000 1570628 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": 1095463, "vin": [ { "gen": { "height": 1095453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1757209384c34184df6a0e11bd60d6b7dc114b35a486a2ee09718d3386cf147" } } ], "extra": [ 1, 184, 23, 61, 40, 174, 93, 204, 176, 128, 215, 199, 2, 143, 0, 180, 155, 231, 157, 59, 88, 7, 189, 242, 65, 63, 202, 250, 101, 4, 165, 131, 123, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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