Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21443977494295ea4732d427c40701df4dee0b04981762b2803fa6e253f3bb94

Tx prefix hash: b673c212486f69a03d5cea69fce92315d3291ca9ab7d6954e078ccf7d775dbc1
Tx public key: b52e1daa66c254d173c0d7f8068f5c2cf7efbdca787ce83f8a5f0995f6215798
Timestamp: 1700909889 Timestamp [UCT]: 2023-11-25 10:58:09 Age [y:d:h:m:s]: 01:096:12:20:57
Block: 899289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330113 RingCT/type: yes/0
Extra: 01b52e1daa66c254d173c0d7f8068f5c2cf7efbdca787ce83f8a5f0995f6215798021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.643105487000 dcy

stealth address amount amount idx
00: 1a94902157c6e88481b29bbfadcff9c478d51ee50abb2c7b16f40ae259200caa 0.643105487000 1355736 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": 899299, "vin": [ { "gen": { "height": 899289 } } ], "vout": [ { "amount": 643105487, "target": { "key": "1a94902157c6e88481b29bbfadcff9c478d51ee50abb2c7b16f40ae259200caa" } } ], "extra": [ 1, 181, 46, 29, 170, 102, 194, 84, 209, 115, 192, 215, 248, 6, 143, 92, 44, 247, 239, 189, 202, 120, 124, 232, 63, 138, 95, 9, 149, 246, 33, 87, 152, 2, 17, 0, 0, 0, 1, 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