Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f9f37cb7d51ea8f09f21392573a8cf273ed75d466c046d1db5d832e7878de45

Tx prefix hash: 6d687f6e2dcbef93a9ea6a51f85aaeb43a2275ab0234b244ad61fc6ed413994e
Tx public key: 8945892736e8ba671e08225a73defa2c4ee04ca12c6138d3973f7395baab745a
Timestamp: 1727153146 Timestamp [UCT]: 2024-09-24 04:45:46 Age [y:d:h:m:s]: 00:121:20:39:09
Block: 1116856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87098 RingCT/type: yes/0
Extra: 018945892736e8ba671e08225a73defa2c4ee04ca12c6138d3973f7395baab745a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acaf9f751cbe1d468028e89934055d7f6c04ccdb4ea1c1da8a40780d61a8d4ac 0.600000000000 1597487 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": 1116866, "vin": [ { "gen": { "height": 1116856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acaf9f751cbe1d468028e89934055d7f6c04ccdb4ea1c1da8a40780d61a8d4ac" } } ], "extra": [ 1, 137, 69, 137, 39, 54, 232, 186, 103, 30, 8, 34, 90, 115, 222, 250, 44, 78, 224, 76, 161, 44, 97, 56, 211, 151, 63, 115, 149, 186, 171, 116, 90, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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