Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc68c286d85ea9078b905c00930739514980fa28379a3b43a103fdaa9c3d985c

Tx prefix hash: 23f0d018920ebbf236801be68fbcffd9c17d0862684282c681160a8ac064b95d
Tx public key: fb7430a379f561e5c1b0f9e12693f97c92e3223cbf8d8525cf4299c8227aa7ee
Timestamp: 1734679008 Timestamp [UCT]: 2024-12-20 07:16:48 Age [y:d:h:m:s]: 00:096:05:19:46
Block: 1179162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68517 RingCT/type: yes/0
Extra: 01fb7430a379f561e5c1b0f9e12693f97c92e3223cbf8d8525cf4299c8227aa7ee0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e8ec176e27eae8d1699a54a5ee2cca64f003356b969e8ecbefbed99e13ed4f 0.600000000000 1665553 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": 1179172, "vin": [ { "gen": { "height": 1179162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e8ec176e27eae8d1699a54a5ee2cca64f003356b969e8ecbefbed99e13ed4f" } } ], "extra": [ 1, 251, 116, 48, 163, 121, 245, 97, 229, 193, 176, 249, 225, 38, 147, 249, 124, 146, 227, 34, 60, 191, 141, 133, 37, 207, 66, 153, 200, 34, 122, 167, 238, 2, 17, 0, 0, 0, 5, 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