Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05468f1ee7e0b8c098c13d692f16e3a6ff154080d86aa3a4cc3b025006c0d7b

Tx prefix hash: b014551dde318415bb5afca7686c91a7b1c0d8fdf05baceb3f3b538d0a38a4fe
Tx public key: 54d11c335b8fc6e2f9d0d3f8a0ed7c83a221f3211346caacce315b1a425d47d9
Timestamp: 1727367606 Timestamp [UCT]: 2024-09-26 16:20:06 Age [y:d:h:m:s]: 00:211:05:40:04
Block: 1118636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150793 RingCT/type: yes/0
Extra: 0154d11c335b8fc6e2f9d0d3f8a0ed7c83a221f3211346caacce315b1a425d47d9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 272308e394ee09333e22c72a240e3bc9911cb4fb3cefa31c3f9485d0e1ebe519 0.600000000000 1599897 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": 1118646, "vin": [ { "gen": { "height": 1118636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "272308e394ee09333e22c72a240e3bc9911cb4fb3cefa31c3f9485d0e1ebe519" } } ], "extra": [ 1, 84, 209, 28, 51, 91, 143, 198, 226, 249, 208, 211, 248, 160, 237, 124, 131, 162, 33, 243, 33, 19, 70, 202, 172, 206, 49, 91, 26, 66, 93, 71, 217, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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