Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1470dce4fec78a64afee528e1f9ba54c6f245cd46e25c49b214ddf170a9d66

Tx prefix hash: b683596dc300fac259b71f5d0f66e5ae248345736c0a1ba6c8111b2e6d95bf9a
Tx public key: 8efd41a2bf56161c5e7e4cac6e9cfdccfdc73bbd4fa0c92ac036ec57cf2e56dc
Timestamp: 1715183035 Timestamp [UCT]: 2024-05-08 15:43:55 Age [y:d:h:m:s]: 00:326:18:21:12
Block: 1017637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233547 RingCT/type: yes/0
Extra: 018efd41a2bf56161c5e7e4cac6e9cfdccfdc73bbd4fa0c92ac036ec57cf2e56dc0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b34aadbd55c4f4bdc1dfd9b2204401c200a307926e30fc804b1f68aff9f05f9 0.600000000000 1481420 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": 1017647, "vin": [ { "gen": { "height": 1017637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b34aadbd55c4f4bdc1dfd9b2204401c200a307926e30fc804b1f68aff9f05f9" } } ], "extra": [ 1, 142, 253, 65, 162, 191, 86, 22, 28, 94, 126, 76, 172, 110, 156, 253, 204, 253, 199, 59, 189, 79, 160, 201, 42, 192, 54, 236, 87, 207, 46, 86, 220, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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