Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10df12b148b665e60be7ceb2c94b25c2a53540e8aa5f8ad01f45e2eb10c5f4bb

Tx prefix hash: 08936e1bae73864f0438ea1c6d77adb2ee44e7090cdaf4375c65265e95e26574
Tx public key: 0ef325321c18fbab8c551cccbf9d0bd8253d89fb8a7d10d24d6ddcd305de59af
Timestamp: 1712281572 Timestamp [UCT]: 2024-04-05 01:46:12 Age [y:d:h:m:s]: 01:278:07:21:35
Block: 993549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457687 RingCT/type: yes/0
Extra: 010ef325321c18fbab8c551cccbf9d0bd8253d89fb8a7d10d24d6ddcd305de59af0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4caf6d28636ae86098bbc4f2e07e71d631382be4c936e4da400219faccbeaa05 0.600000000000 1453935 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": 993559, "vin": [ { "gen": { "height": 993549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4caf6d28636ae86098bbc4f2e07e71d631382be4c936e4da400219faccbeaa05" } } ], "extra": [ 1, 14, 243, 37, 50, 28, 24, 251, 171, 140, 85, 28, 204, 191, 157, 11, 216, 37, 61, 137, 251, 138, 125, 16, 210, 77, 109, 220, 211, 5, 222, 89, 175, 2, 17, 0, 0, 0, 1, 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