Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4426a3343e13cca95c09b8d92ddbb76bb8cac7ff4fc8824ecaa7231f0292ee95

Tx prefix hash: 141ac1ca2fdcaf31aad2dc84a1087210d718d9ba3dc09aa316a2db3f0b7659de
Tx public key: 2d0b9ffbb950c5cff073288686c9a8ff06b31062335bb1a206efe20ff277f9b2
Timestamp: 1712501188 Timestamp [UCT]: 2024-04-07 14:46:28 Age [y:d:h:m:s]: 01:214:08:41:54
Block: 995360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411900 RingCT/type: yes/0
Extra: 012d0b9ffbb950c5cff073288686c9a8ff06b31062335bb1a206efe20ff277f9b202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1f3ac41531ea9d3fdd21f4d3fbd52a8981095f7484ceb40a3502feceaeb5b86 0.600000000000 1455768 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": 995370, "vin": [ { "gen": { "height": 995360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f3ac41531ea9d3fdd21f4d3fbd52a8981095f7484ceb40a3502feceaeb5b86" } } ], "extra": [ 1, 45, 11, 159, 251, 185, 80, 197, 207, 240, 115, 40, 134, 134, 201, 168, 255, 6, 179, 16, 98, 51, 91, 177, 162, 6, 239, 226, 15, 242, 119, 249, 178, 2, 17, 0, 0, 0, 7, 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