Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead0cb3e1b61042f17bd8f337c8ea413b0c19e42693297cc0f9a32661f6cd521

Tx prefix hash: 22968bceda70a0cf252523a250234e0b97ad8ac9a5b0dd0bedb5f9f74f43611f
Tx public key: 97d2570522183df80f7504a3a1c7c3e5ee5524cfc978e227ace5fd2226291f15
Timestamp: 1584274189 Timestamp [UCT]: 2020-03-15 12:09:49 Age [y:d:h:m:s]: 04:356:17:17:18
Block: 82877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150297 RingCT/type: yes/0
Extra: 0197d2570522183df80f7504a3a1c7c3e5ee5524cfc978e227ace5fd2226291f15021100000007d81c26c0000000000000000000

1 output(s) for total of 326.133101698000 dcy

stealth address amount amount idx
00: 6466b49576d91413c3c5aab4cec73266789f35d88a453477d6dc4f5e7e94310b 326.133101698000 150993 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": 82887, "vin": [ { "gen": { "height": 82877 } } ], "vout": [ { "amount": 326133101698, "target": { "key": "6466b49576d91413c3c5aab4cec73266789f35d88a453477d6dc4f5e7e94310b" } } ], "extra": [ 1, 151, 210, 87, 5, 34, 24, 61, 248, 15, 117, 4, 163, 161, 199, 195, 229, 238, 85, 36, 207, 201, 120, 226, 39, 172, 229, 253, 34, 38, 41, 31, 21, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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