Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c47111a19582f6b2dae8d8b12e55a3d7303dc525c66a640abeb70834502869aa

Tx prefix hash: 563b80681d73ec4c20da1fe1bea5ae5d4c4243155297afb4607dea1d562aa456
Tx public key: 837db063596185f87dd3eeb08aae772c17d57d9870230644b41a3b10ac447f73
Timestamp: 1693912058 Timestamp [UCT]: 2023-09-05 11:07:38 Age [y:d:h:m:s]: 01:215:06:50:40
Block: 841451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414970 RingCT/type: yes/0
Extra: 01837db063596185f87dd3eeb08aae772c17d57d9870230644b41a3b10ac447f73021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.999824105000 dcy

stealth address amount amount idx
00: c1b844057c2d30d1279f57a58a66317fc08eb681bcf1b15d0ce40d12efb65b47 0.999824105000 1294483 of 0

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": 841461, "vin": [ { "gen": { "height": 841451 } } ], "vout": [ { "amount": 999824105, "target": { "key": "c1b844057c2d30d1279f57a58a66317fc08eb681bcf1b15d0ce40d12efb65b47" } } ], "extra": [ 1, 131, 125, 176, 99, 89, 97, 133, 248, 125, 211, 238, 176, 138, 174, 119, 44, 23, 213, 125, 152, 112, 35, 6, 68, 180, 26, 59, 16, 172, 68, 127, 115, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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