Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28e51aee73412b3e407195ab0baeb4372610bca9a08f2104ae31e4e5b8eb133

Tx prefix hash: f0d755fe6260f59d40b5181d75e0e079ebdac5c96cfd1e116662eacd08b24867
Tx public key: 367e30f3a90964a0b3e508bd7b47d15546534a1026411f30f3dd09f9bd81d5d8
Timestamp: 1719694819 Timestamp [UCT]: 2024-06-29 21:00:19 Age [y:d:h:m:s]: 01:132:22:20:18
Block: 1055013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353558 RingCT/type: yes/0
Extra: 01367e30f3a90964a0b3e508bd7b47d15546534a1026411f30f3dd09f9bd81d5d802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43fd712ae320f2074b333562f17dcf2753e0f6822c86a8fe89087bce2f970bc7 0.600000000000 1525406 of 15

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": 1055023, "vin": [ { "gen": { "height": 1055013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43fd712ae320f2074b333562f17dcf2753e0f6822c86a8fe89087bce2f970bc7" } } ], "extra": [ 1, 54, 126, 48, 243, 169, 9, 100, 160, 179, 229, 8, 189, 123, 71, 209, 85, 70, 83, 74, 16, 38, 65, 31, 48, 243, 221, 9, 249, 189, 129, 213, 216, 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