Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593f80a221f639794c9560378983537553cefaf4672f77ee0e91cc4991853beb

Tx prefix hash: e6557966d9651e6f667dd571be9e5161ff67162a78d7721e949af886e1caeafc
Tx public key: 150ecfcfd64aa28c4d5b1f679b324b2c48cebde4820a69d5416472a569f69e17
Timestamp: 1577793217 Timestamp [UCT]: 2019-12-31 11:53:37 Age [y:d:h:m:s]: 05:002:19:57:25
Block: 35703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152026 RingCT/type: yes/0
Extra: 01150ecfcfd64aa28c4d5b1f679b324b2c48cebde4820a69d5416472a569f69e170211000000028a2ee0d9000000000000000000

1 output(s) for total of 467.440378829000 dcy

stealth address amount amount idx
00: d2541016ac163579a7b57ef6b933fbc46bfd52f6b316ea6c5c070c2c9ca9eb95 467.440378829000 60276 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": 35713, "vin": [ { "gen": { "height": 35703 } } ], "vout": [ { "amount": 467440378829, "target": { "key": "d2541016ac163579a7b57ef6b933fbc46bfd52f6b316ea6c5c070c2c9ca9eb95" } } ], "extra": [ 1, 21, 14, 207, 207, 214, 74, 162, 140, 77, 91, 31, 103, 155, 50, 75, 44, 72, 206, 189, 228, 130, 10, 105, 213, 65, 100, 114, 165, 105, 246, 158, 23, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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