Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1c10a1e59540de3e68b77f978ca2d9e7e9693b0dbf289fb20d987021cca65d4

Tx prefix hash: 527d567c2f9490dc35c394676601a3066165cce9e1892d98bbafb4a8a056ba70
Tx public key: 51b0f595d16e09f20d5db5604a39324a473429188b6865f3f49d656141d1575b
Timestamp: 1634934221 Timestamp [UCT]: 2021-10-22 20:23:41 Age [y:d:h:m:s]: 03:067:15:33:56
Block: 358330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826662 RingCT/type: yes/0
Extra: 0151b0f595d16e09f20d5db5604a39324a473429188b6865f3f49d656141d1575b0211000000014a0f5013000000000000000000

1 output(s) for total of 39.875337466000 dcy

stealth address amount amount idx
00: 488cc85420d5683f9ec7b4e764bb47b548329676d6b65cefe34f8fd1fa035486 39.875337466000 730191 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": 358340, "vin": [ { "gen": { "height": 358330 } } ], "vout": [ { "amount": 39875337466, "target": { "key": "488cc85420d5683f9ec7b4e764bb47b548329676d6b65cefe34f8fd1fa035486" } } ], "extra": [ 1, 81, 176, 245, 149, 209, 110, 9, 242, 13, 93, 181, 96, 74, 57, 50, 74, 71, 52, 41, 24, 139, 104, 101, 243, 244, 157, 101, 97, 65, 209, 87, 91, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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