Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6d2e644323f7ac6d6f4d8161aca2e4c4d3cab192e084051bef7f47147baf7d

Tx prefix hash: 0e9c975dbf05df7d9594c020eb8fa87de3cb4bae6f3ec01a400cd7c9b456d33e
Tx public key: 8a049f3f92e57f1341116b52ad3562a2f255a62e3ea045fdadf3cc77baf81600
Timestamp: 1700929618 Timestamp [UCT]: 2023-11-25 16:26:58 Age [y:d:h:m:s]: 01:096:06:11:52
Block: 899450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329931 RingCT/type: yes/0
Extra: 018a049f3f92e57f1341116b52ad3562a2f255a62e3ea045fdadf3cc77baf81600021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.642316021000 dcy

stealth address amount amount idx
00: ba45fac58e8ee73d97f70ab9f44bd0894bbf475c77a0e29b86622679d10f974b 0.642316021000 1355905 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": 899460, "vin": [ { "gen": { "height": 899450 } } ], "vout": [ { "amount": 642316021, "target": { "key": "ba45fac58e8ee73d97f70ab9f44bd0894bbf475c77a0e29b86622679d10f974b" } } ], "extra": [ 1, 138, 4, 159, 63, 146, 229, 127, 19, 65, 17, 107, 82, 173, 53, 98, 162, 242, 85, 166, 46, 62, 160, 69, 253, 173, 243, 204, 119, 186, 248, 22, 0, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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