Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb974842710bb770f980d2b7ea462fe57d179e959a26136068080f86659b7767

Tx prefix hash: 38da53af363861c7a2e1ce29a7ed4fe88c5bc0bddaeb835ec45e72d4a6c9ee49
Tx public key: caeeaf33a0c7fad6c8be12283a41e9ece7c742fe223b535b084c854c791b60e9
Timestamp: 1734667182 Timestamp [UCT]: 2024-12-20 03:59:42 Age [y:d:h:m:s]: 00:112:00:55:51
Block: 1179060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79852 RingCT/type: yes/0
Extra: 01caeeaf33a0c7fad6c8be12283a41e9ece7c742fe223b535b084c854c791b60e9021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93a35c512a769696a8663d120a0d789fab74d3e68c51afb071c5cae994ea1d9a 0.600000000000 1665451 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": 1179070, "vin": [ { "gen": { "height": 1179060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93a35c512a769696a8663d120a0d789fab74d3e68c51afb071c5cae994ea1d9a" } } ], "extra": [ 1, 202, 238, 175, 51, 160, 199, 250, 214, 200, 190, 18, 40, 58, 65, 233, 236, 231, 199, 66, 254, 34, 59, 83, 91, 8, 76, 133, 76, 121, 27, 96, 233, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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