Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8ce9d2bf8e95cc2e889282bddfcb2acf18af4198b05c08f611511250611eb3

Tx prefix hash: 18dd3d88f418762c522a74434d5f7d2cff4df1ee9170887d08b3041cc23c9d3e
Tx public key: bf71a52003446d61e0affbb99f22bb9947a568cbf2a5372f6ab86a99ba37abce
Timestamp: 1702067107 Timestamp [UCT]: 2023-12-08 20:25:07 Age [y:d:h:m:s]: 01:120:14:24:23
Block: 908881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347328 RingCT/type: yes/0
Extra: 01bf71a52003446d61e0affbb99f22bb9947a568cbf2a5372f6ab86a99ba37abce02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07343dec3a83c7c8b6379db92ccfa4c0d27c287017c3cfa2bdf4c4f6eaec7e0e 0.600000000000 1365938 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": 908891, "vin": [ { "gen": { "height": 908881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07343dec3a83c7c8b6379db92ccfa4c0d27c287017c3cfa2bdf4c4f6eaec7e0e" } } ], "extra": [ 1, 191, 113, 165, 32, 3, 68, 109, 97, 224, 175, 251, 185, 159, 34, 187, 153, 71, 165, 104, 203, 242, 165, 55, 47, 106, 184, 106, 153, 186, 55, 171, 206, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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