Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a05e6ed0cea8ab304eb41d448c6d177f2a0939811df8d3bbbda546eb960e307

Tx prefix hash: cd56163b7810fe2f6340a419a13a312d21b76ed9f1c671a128a4ad08e03f4840
Tx public key: 2c80d3e4275afdc030861bacb69ec9677b907e23149c2e2ee68d36e919661ef8
Timestamp: 1712860739 Timestamp [UCT]: 2024-04-11 18:38:59 Age [y:d:h:m:s]: 01:035:22:45:08
Block: 998341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286687 RingCT/type: yes/0
Extra: 012c80d3e4275afdc030861bacb69ec9677b907e23149c2e2ee68d36e919661ef80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 660c4106b05f84fbcce061cd71fbe56465b808407540d9f705e3f11f4b9ec5e2 0.600000000000 1458787 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": 998351, "vin": [ { "gen": { "height": 998341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "660c4106b05f84fbcce061cd71fbe56465b808407540d9f705e3f11f4b9ec5e2" } } ], "extra": [ 1, 44, 128, 211, 228, 39, 90, 253, 192, 48, 134, 27, 172, 182, 158, 201, 103, 123, 144, 126, 35, 20, 156, 46, 46, 230, 141, 54, 233, 25, 102, 30, 248, 2, 17, 0, 0, 0, 3, 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