Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e060cd1c812d155610a0bf459d03f9d3690caa63086a8365465fdf0b4135c274

Tx prefix hash: b434a5071383d00246b31929780e3e4bdd6311dadfc970371293d40cf90ce8b1
Tx public key: 4c8e65553a3a500d40d8dc4fe7bf9ef6ef5973a316b7bfec99d951cef028e876
Timestamp: 1716127064 Timestamp [UCT]: 2024-05-19 13:57:44 Age [y:d:h:m:s]: 00:325:14:23:55
Block: 1025444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232732 RingCT/type: yes/0
Extra: 014c8e65553a3a500d40d8dc4fe7bf9ef6ef5973a316b7bfec99d951cef028e87602110000000159dad3f5000000000000000000

1 output(s) for total of 0.613580000000 dcy

stealth address amount amount idx
00: 8146f6d7a57386ee76a1c25eba48d1298707aada9f9aede57c57bb64f140181a 0.613580000000 1491955 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": 1025454, "vin": [ { "gen": { "height": 1025444 } } ], "vout": [ { "amount": 613580000, "target": { "key": "8146f6d7a57386ee76a1c25eba48d1298707aada9f9aede57c57bb64f140181a" } } ], "extra": [ 1, 76, 142, 101, 85, 58, 58, 80, 13, 64, 216, 220, 79, 231, 191, 158, 246, 239, 89, 115, 163, 22, 183, 191, 236, 153, 217, 81, 206, 240, 40, 232, 118, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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