Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e0296e580b11d8430ef3aadc534a0364c88a4f1d48889a574de2c5778f4c9d

Tx prefix hash: 484bb6c62cbeb9a11786172ea07919c468a555d7e46d332f824ae37d4b72a2e1
Tx public key: 6f2fab9be488d0e0a2b6e1a1b374fb8d6882451601ad57567df397993f617d2c
Timestamp: 1578798924 Timestamp [UCT]: 2020-01-12 03:15:24 Age [y:d:h:m:s]: 04:356:17:11:31
Block: 43606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144495 RingCT/type: yes/0
Extra: 016f2fab9be488d0e0a2b6e1a1b374fb8d6882451601ad57567df397993f617d2c0211000000094ac5aa02000000000000000000

1 output(s) for total of 440.071823571000 dcy

stealth address amount amount idx
00: bf6357e823566e178e136468fce098d0ca58ba868b958e52e19b3efb5fe7865d 440.071823571000 79045 of 0

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": 43616, "vin": [ { "gen": { "height": 43606 } } ], "vout": [ { "amount": 440071823571, "target": { "key": "bf6357e823566e178e136468fce098d0ca58ba868b958e52e19b3efb5fe7865d" } } ], "extra": [ 1, 111, 47, 171, 155, 228, 136, 208, 224, 162, 182, 225, 161, 179, 116, 251, 141, 104, 130, 69, 22, 1, 173, 87, 86, 125, 243, 151, 153, 63, 97, 125, 44, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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