Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fda64b67d4c845fbc21becf3df9b4dc020b40a64845834812e2d34ce8e8cc0

Tx prefix hash: 83a0f09b5e94e7e5fad4265bf37f766641d1effdbf3214c22c59b0351d01fbe8
Tx public key: 4d448a70a481fbf95754d11428bc1759720fd1c83e8a50f4423cb99ba4954fa7
Timestamp: 1696179593 Timestamp [UCT]: 2023-10-01 16:59:53 Age [y:d:h:m:s]: 01:145:14:27:45
Block: 860274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365064 RingCT/type: yes/0
Extra: 014d448a70a481fbf95754d11428bc1759720fd1c83e8a50f4423cb99ba4954fa702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.866074323000 dcy

stealth address amount amount idx
00: 6ccd1b1e4b6e273cc66a764ad04c85e36d2d99157ca40272f21527201e622bb4 0.866074323000 1314550 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": 860284, "vin": [ { "gen": { "height": 860274 } } ], "vout": [ { "amount": 866074323, "target": { "key": "6ccd1b1e4b6e273cc66a764ad04c85e36d2d99157ca40272f21527201e622bb4" } } ], "extra": [ 1, 77, 68, 138, 112, 164, 129, 251, 249, 87, 84, 209, 20, 40, 188, 23, 89, 114, 15, 209, 200, 62, 138, 80, 244, 66, 60, 185, 155, 164, 149, 79, 167, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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