Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f4a66092c7e9b02c6a97cb6d6ddb0b32a0e07c4e9ef208a09e8b2419b269d3

Tx prefix hash: d09bf9e9f9264def18412d789c25c02f9acd5ffd1f9dc527ad2054e369968295
Tx public key: 644aa30c775f7b109f06ea44ea61c8eb8f4d2eefc957f5facf1c67126896a71b
Timestamp: 1696533423 Timestamp [UCT]: 2023-10-05 19:17:03 Age [y:d:h:m:s]: 01:013:17:59:09
Block: 863205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271104 RingCT/type: yes/0
Extra: 01644aa30c775f7b109f06ea44ea61c8eb8f4d2eefc957f5facf1c67126896a71b02110000000efaf35c9c000000000000000000

1 output(s) for total of 0.846922243000 dcy

stealth address amount amount idx
00: 7128ac8eef98ff2a54b7f074ddec6cc235e3a91b54c7a5b129d81606bc24032d 0.846922243000 1317653 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": 863215, "vin": [ { "gen": { "height": 863205 } } ], "vout": [ { "amount": 846922243, "target": { "key": "7128ac8eef98ff2a54b7f074ddec6cc235e3a91b54c7a5b129d81606bc24032d" } } ], "extra": [ 1, 100, 74, 163, 12, 119, 95, 123, 16, 159, 6, 234, 68, 234, 97, 200, 235, 143, 77, 46, 239, 201, 87, 245, 250, 207, 28, 103, 18, 104, 150, 167, 27, 2, 17, 0, 0, 0, 14, 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