Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3b1d46653dbf6374f930848e2a820212146c0bcd423c1c4770e78fb97e3f1dc

Tx prefix hash: 04c7d0b79be279f6d9c6a695ee0b0da609ec563a85ee570ec38baab645ccbec1
Tx public key: 4a88e8992788f8d15794a19164464d345a9a833d72ef8961d846463868e9c5b7
Timestamp: 1715004433 Timestamp [UCT]: 2024-05-06 14:07:13 Age [y:d:h:m:s]: 00:325:23:42:10
Block: 1016138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233017 RingCT/type: yes/0
Extra: 014a88e8992788f8d15794a19164464d345a9a833d72ef8961d846463868e9c5b70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec68aa541c28a16658ad0ed24653bf3f4ae3dd673e7f7cc1a654bda5ffa3ee79 0.600000000000 1479637 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": 1016148, "vin": [ { "gen": { "height": 1016138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec68aa541c28a16658ad0ed24653bf3f4ae3dd673e7f7cc1a654bda5ffa3ee79" } } ], "extra": [ 1, 74, 136, 232, 153, 39, 136, 248, 209, 87, 148, 161, 145, 100, 70, 77, 52, 90, 154, 131, 61, 114, 239, 137, 97, 216, 70, 70, 56, 104, 233, 197, 183, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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