Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cb8a7f527c06f73fb8858a7752b9e0a164b91a6c0838b67d37c2d009b080524

Tx prefix hash: 2b2ae462aa28f4bdffe3ff121f754842b4969d61cc68a766d89b50c0ba5b344e
Tx public key: 4bc2a94fcd4022091de54c0455fb4e50d6fc0d3ae6eacae44c6027df8cb08b09
Timestamp: 1733190954 Timestamp [UCT]: 2024-12-03 01:55:54 Age [y:d:h:m:s]: 00:118:00:20:17
Block: 1166815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84140 RingCT/type: yes/0
Extra: 014bc2a94fcd4022091de54c0455fb4e50d6fc0d3ae6eacae44c6027df8cb08b09021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86cd39376158313e2b263871b2d40c78e72e4e62b9b393990c1ae9487b9a4c38 0.600000000000 1652506 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": 1166825, "vin": [ { "gen": { "height": 1166815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86cd39376158313e2b263871b2d40c78e72e4e62b9b393990c1ae9487b9a4c38" } } ], "extra": [ 1, 75, 194, 169, 79, 205, 64, 34, 9, 29, 229, 76, 4, 85, 251, 78, 80, 214, 252, 13, 58, 230, 234, 202, 228, 76, 96, 39, 223, 140, 176, 139, 9, 2, 17, 0, 0, 0, 5, 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