Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fc978be00c5a7b7e3bdd99df585c621c920aae0539e358e117e1823ef4c29d5

Tx prefix hash: 6648c281a1771d6006fcdc353f5cb29a21a7b89951c4d0d5f582e4a0c73ea669
Tx public key: 3f292c95eaaee5df6b2119c3782c8da2feb3a7b43b3eeb7ac681b2b30d8dfe47
Timestamp: 1705986991 Timestamp [UCT]: 2024-01-23 05:16:31 Age [y:d:h:m:s]: 00:295:07:04:02
Block: 941346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211464 RingCT/type: yes/0
Extra: 013f292c95eaaee5df6b2119c3782c8da2feb3a7b43b3eeb7ac681b2b30d8dfe470211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 579c883f24a49cf648fbf50a5010e5b0c435dd69f8b127be53a800755f27eb72 0.600000000000 1399492 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": 941356, "vin": [ { "gen": { "height": 941346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "579c883f24a49cf648fbf50a5010e5b0c435dd69f8b127be53a800755f27eb72" } } ], "extra": [ 1, 63, 41, 44, 149, 234, 174, 229, 223, 107, 33, 25, 195, 120, 44, 141, 162, 254, 179, 167, 180, 59, 62, 235, 122, 198, 129, 178, 179, 13, 141, 254, 71, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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