Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6959f00051fa4b0f9de7ac7323d96fd0abfd9e44b959880736dcf5f8aff27e58

Tx prefix hash: c436b24f1f8def281a548fe4815933c14cf602caf7d73c814a60a60706e443a4
Tx public key: 88af41f00de5f62260db6f8ae1aa1771ec049b8d3056d8db973d9657c3297718
Timestamp: 1648933647 Timestamp [UCT]: 2022-04-02 21:07:27 Age [y:d:h:m:s]: 02:211:08:18:31
Block: 471885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670710 RingCT/type: yes/0
Extra: 0188af41f00de5f62260db6f8ae1aa1771ec049b8d3056d8db973d9657c329771802110000000337cb3088000000000000000000

1 output(s) for total of 16.766767916000 dcy

stealth address amount amount idx
00: fc8613eb6a8f6b5eedbd5c9b3de0e68ff40565f4d6fab183ccbbf267889936d9 16.766767916000 891309 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": 471895, "vin": [ { "gen": { "height": 471885 } } ], "vout": [ { "amount": 16766767916, "target": { "key": "fc8613eb6a8f6b5eedbd5c9b3de0e68ff40565f4d6fab183ccbbf267889936d9" } } ], "extra": [ 1, 136, 175, 65, 240, 13, 229, 246, 34, 96, 219, 111, 138, 225, 170, 23, 113, 236, 4, 155, 141, 48, 86, 216, 219, 151, 61, 150, 87, 195, 41, 119, 24, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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