Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c09e6521f2a8410030374d3565e071a0250af17f7f210262c4873622475f01a7

Tx prefix hash: ab2e239dbf02e87e157f9c9907659257f3493df04a5e532a6abf91ed63ffa6a4
Tx public key: 32fdd1f0e4f467c3fdb60c7637e531c64588a8d3e0eb6408da347636909cfafd
Timestamp: 1725440039 Timestamp [UCT]: 2024-09-04 08:53:59 Age [y:d:h:m:s]: 01:090:12:14:19
Block: 1102656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323153 RingCT/type: yes/0
Extra: 0132fdd1f0e4f467c3fdb60c7637e531c64588a8d3e0eb6408da347636909cfafd02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b05e8c45807381e75c1e39ec70286d2da7954bff542cf53e398f0f93d56f1f6b 0.600000000000 1579179 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": 1102666, "vin": [ { "gen": { "height": 1102656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b05e8c45807381e75c1e39ec70286d2da7954bff542cf53e398f0f93d56f1f6b" } } ], "extra": [ 1, 50, 253, 209, 240, 228, 244, 103, 195, 253, 182, 12, 118, 55, 229, 49, 198, 69, 136, 168, 211, 224, 235, 100, 8, 218, 52, 118, 54, 144, 156, 250, 253, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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