Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc79ac4c1d0fd8fc01b0ccaec238cf20384bd7fe4a94b3d1f57abef5c2b72c92

Tx prefix hash: 3ae223eb9152fd12fc89858b8a626eaa81ba6d339ab2574c4fa2dae7c7add5c7
Tx public key: ac46afef7fc85bb7462b2cebf49f98a88f3dcc8e203538a5e102f77aa35ded86
Timestamp: 1737039219 Timestamp [UCT]: 2025-01-16 14:53:39 Age [y:d:h:m:s]: 00:152:00:53:57
Block: 1198671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108375 RingCT/type: yes/0
Extra: 01ac46afef7fc85bb7462b2cebf49f98a88f3dcc8e203538a5e102f77aa35ded860211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90a9624e5000e05fd503fc05e915202a8fcab4df7a70f05292b4d0aab34747aa 0.600000000000 1685296 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": 1198681, "vin": [ { "gen": { "height": 1198671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90a9624e5000e05fd503fc05e915202a8fcab4df7a70f05292b4d0aab34747aa" } } ], "extra": [ 1, 172, 70, 175, 239, 127, 200, 91, 183, 70, 43, 44, 235, 244, 159, 152, 168, 143, 61, 204, 142, 32, 53, 56, 165, 225, 2, 247, 122, 163, 93, 237, 134, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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