Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 515f45c0a7a372dc6cceffac98a85c17eeaeb854c3a042ac8c23280a3b9c867d

Tx prefix hash: c1012a5f9d5716d14f0cc2c868bab0c86a8f901f346885e2cb49813c2bf95515
Tx public key: 7e475c7f00f4e9e3c766eee0890055b678375664644a8ce85d052da11bb56435
Timestamp: 1582805109 Timestamp [UCT]: 2020-02-27 12:05:09 Age [y:d:h:m:s]: 05:055:23:31:20
Block: 73114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193861 RingCT/type: yes/0
Extra: 017e475c7f00f4e9e3c766eee0890055b678375664644a8ce85d052da11bb564350211000000010aca7173000000000000000000

1 output(s) for total of 351.353080881000 dcy

stealth address amount amount idx
00: 8b6f4804fe858273651da54d0ed0336f1f90b655ab3c1ee1316e6a99e5389f45 351.353080881000 134784 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": 73124, "vin": [ { "gen": { "height": 73114 } } ], "vout": [ { "amount": 351353080881, "target": { "key": "8b6f4804fe858273651da54d0ed0336f1f90b655ab3c1ee1316e6a99e5389f45" } } ], "extra": [ 1, 126, 71, 92, 127, 0, 244, 233, 227, 199, 102, 238, 224, 137, 0, 85, 182, 120, 55, 86, 100, 100, 74, 140, 232, 93, 5, 45, 161, 27, 181, 100, 53, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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