Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ba6039f764d906a85a1598312b873b85e640d45ed023e5464f9f186a9f496e0

Tx prefix hash: c46e93ee307a38036f7051b59b2f83e393103b789dc539b27f27c33be121db8f
Tx public key: e85b0536b4f6aa4338c001c431f15ed972e6c76910bfd036a1df7e959d582142
Timestamp: 1702742471 Timestamp [UCT]: 2023-12-16 16:01:11 Age [y:d:h:m:s]: 01:072:02:15:16
Block: 914483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312623 RingCT/type: yes/0
Extra: 01e85b0536b4f6aa4338c001c431f15ed972e6c76910bfd036a1df7e959d58214202110000000dfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65fdc1571eccc6395538ad49ce4fe41ef491c684bfd6b5fcc55e554263f5a474 0.600000000000 1371799 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": 914493, "vin": [ { "gen": { "height": 914483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65fdc1571eccc6395538ad49ce4fe41ef491c684bfd6b5fcc55e554263f5a474" } } ], "extra": [ 1, 232, 91, 5, 54, 180, 246, 170, 67, 56, 192, 1, 196, 49, 241, 94, 217, 114, 230, 199, 105, 16, 191, 208, 54, 161, 223, 126, 149, 157, 88, 33, 66, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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