Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3d6f2aa9c2389f4a00f43ac93b688d065ef99a432b3246a3c1ff1ca3686942

Tx prefix hash: 5eb4eb2cd7200b50d342aa1b2a1339bb07e0ad49484b09f6bcc0179db8b6b76c
Tx public key: 10a916efa7fc87b3fffed758b4fc1387c50e40a0dbece66450510f0ebc11e7c4
Timestamp: 1580853884 Timestamp [UCT]: 2020-02-04 22:04:44 Age [y:d:h:m:s]: 05:005:17:34:50
Block: 58663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156220 RingCT/type: yes/0
Extra: 0110a916efa7fc87b3fffed758b4fc1387c50e40a0dbece66450510f0ebc11e7c40211000000012264afe6000000000000000000

1 output(s) for total of 392.306902199000 dcy

stealth address amount amount idx
00: 5e1ca21958aa8f0bd96da43e96d017af1b59836ae3a4eb7caecbe4b37282b1d5 392.306902199000 108419 of 0

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": 58673, "vin": [ { "gen": { "height": 58663 } } ], "vout": [ { "amount": 392306902199, "target": { "key": "5e1ca21958aa8f0bd96da43e96d017af1b59836ae3a4eb7caecbe4b37282b1d5" } } ], "extra": [ 1, 16, 169, 22, 239, 167, 252, 135, 179, 255, 254, 215, 88, 180, 252, 19, 135, 197, 14, 64, 160, 219, 236, 230, 100, 80, 81, 15, 14, 188, 17, 231, 196, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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