Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b62d4a5054ede9aa34702558e2dd67dad1007454be87a8bd42d32e55c0b222e

Tx prefix hash: 89d0278d9cb47e722952cad37ae9b29405c337d5d6cbd643d20d57fabf65b6bd
Tx public key: ee30acddd674b57d1acc6a782931f225841cecb7197fe657e64f47e910cb9e35
Timestamp: 1686508849 Timestamp [UCT]: 2023-06-11 18:40:49 Age [y:d:h:m:s]: 01:311:15:39:11
Block: 780160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483918 RingCT/type: yes/0
Extra: 01ee30acddd674b57d1acc6a782931f225841cecb7197fe657e64f47e910cb9e35021100000001272bcc39000000000000000000

1 output(s) for total of 1.595902001000 dcy

stealth address amount amount idx
00: 844e0dcf98a7bf848c90f027f6eec3b07641926c780b66f29f7908b87a0c5924 1.595902001000 1229859 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": 780170, "vin": [ { "gen": { "height": 780160 } } ], "vout": [ { "amount": 1595902001, "target": { "key": "844e0dcf98a7bf848c90f027f6eec3b07641926c780b66f29f7908b87a0c5924" } } ], "extra": [ 1, 238, 48, 172, 221, 214, 116, 181, 125, 26, 204, 106, 120, 41, 49, 242, 37, 132, 28, 236, 183, 25, 127, 230, 87, 230, 79, 71, 233, 16, 203, 158, 53, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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