Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11d23b429c7755cd4ae061b66c5947d2e6684b9a0e124da40d187ac9a59cf2b3

Tx prefix hash: 36d663d96af5a6562dfeb7070f52c66fae64fabb16878e5950c9e8e5254d64f9
Tx public key: 5c4eb9c9a70a8eeb4ed5b686001c68959aae1ffff8ea1636ff4c4100bb044d25
Timestamp: 1720101069 Timestamp [UCT]: 2024-07-04 13:51:09 Age [y:d:h:m:s]: 00:315:02:35:56
Block: 1058386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225183 RingCT/type: yes/0
Extra: 015c4eb9c9a70a8eeb4ed5b686001c68959aae1ffff8ea1636ff4c4100bb044d250211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0881bdbb13523289d5d0ed9b75c27a1dd9bd12a99a824878394d23103622896e 0.600000000000 1528841 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": 1058396, "vin": [ { "gen": { "height": 1058386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0881bdbb13523289d5d0ed9b75c27a1dd9bd12a99a824878394d23103622896e" } } ], "extra": [ 1, 92, 78, 185, 201, 167, 10, 142, 235, 78, 213, 182, 134, 0, 28, 104, 149, 154, 174, 31, 255, 248, 234, 22, 54, 255, 76, 65, 0, 187, 4, 77, 37, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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