Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa67a9878b4abbbcb70e5cfb74391a3cfa517c8c00ec1d2ae69ab6d3ed7753ea

Tx prefix hash: 28f39f3e020cdc66cd06a93a8dbad8317471a193e204314ad0e3be0461be6d2e
Tx public key: dd8a7ea815576491cbf6886270a8a48811d3f37a97a2ce2e283a28f0285934c8
Timestamp: 1704175246 Timestamp [UCT]: 2024-01-02 06:00:46 Age [y:d:h:m:s]: 01:054:23:10:41
Block: 926352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300361 RingCT/type: yes/0
Extra: 01dd8a7ea815576491cbf6886270a8a48811d3f37a97a2ce2e283a28f0285934c8021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47dfaadf63439d6384474a7e64663c3ca4b7cf3b218fa8e3253b4380539453e5 0.600000000000 1384134 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": 926362, "vin": [ { "gen": { "height": 926352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47dfaadf63439d6384474a7e64663c3ca4b7cf3b218fa8e3253b4380539453e5" } } ], "extra": [ 1, 221, 138, 126, 168, 21, 87, 100, 145, 203, 246, 136, 98, 112, 168, 164, 136, 17, 211, 243, 122, 151, 162, 206, 46, 40, 58, 40, 240, 40, 89, 52, 200, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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