Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b69d3e33590878be2c7721f7240498ede0210b1dd2473d1276deb8ef6613809

Tx prefix hash: dd2822dbe2c473a6313efbf47aea8914b3998702480bcdfbee7a3566c31853f5
Tx public key: 4bf3c5b08fa5e3df5a35951853d338d39a061f1a3e1779af5dd4473dad24aaa4
Timestamp: 1722021184 Timestamp [UCT]: 2024-07-26 19:13:04 Age [y:d:h:m:s]: 00:306:09:37:05
Block: 1074311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218943 RingCT/type: yes/0
Extra: 014bf3c5b08fa5e3df5a35951853d338d39a061f1a3e1779af5dd4473dad24aaa4021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e1561fe24f1cf6af3087b0fd344e800a1ef619b3018fb9a369ea4e480d60f31 0.600000000000 1546824 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": 1074321, "vin": [ { "gen": { "height": 1074311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e1561fe24f1cf6af3087b0fd344e800a1ef619b3018fb9a369ea4e480d60f31" } } ], "extra": [ 1, 75, 243, 197, 176, 143, 165, 227, 223, 90, 53, 149, 24, 83, 211, 56, 211, 154, 6, 31, 26, 62, 23, 121, 175, 93, 212, 71, 61, 173, 36, 170, 164, 2, 17, 0, 0, 0, 9, 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