Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f34560517208fa620d091653d3230972d96e358b82f718b1fe4f4c51a8ed7b9

Tx prefix hash: 479aead77358135b3fc431af1199ba6852c7df20d49e065dcf6096abe4f83c01
Tx public key: ec4c99b9dc24bc3a465e8c0e17f8a1f57c8d2425e6755bb29e1cd1c9913cbd27
Timestamp: 1630864268 Timestamp [UCT]: 2021-09-05 17:51:08 Age [y:d:h:m:s]: 03:081:09:00:21
Block: 328054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 833062 RingCT/type: yes/0
Extra: 01ec4c99b9dc24bc3a465e8c0e17f8a1f57c8d2425e6755bb29e1cd1c9913cbd2702110000000cbaa4486c000000000000000000

1 output(s) for total of 50.236730354000 dcy

stealth address amount amount idx
00: 45ad3a2fa9c97fdc92e1ed317a3fad513b251120079d35025773ad18c8dfa63a 50.236730354000 679143 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": 328064, "vin": [ { "gen": { "height": 328054 } } ], "vout": [ { "amount": 50236730354, "target": { "key": "45ad3a2fa9c97fdc92e1ed317a3fad513b251120079d35025773ad18c8dfa63a" } } ], "extra": [ 1, 236, 76, 153, 185, 220, 36, 188, 58, 70, 94, 140, 14, 23, 248, 161, 245, 124, 141, 36, 37, 230, 117, 91, 178, 158, 28, 209, 201, 145, 60, 189, 39, 2, 17, 0, 0, 0, 12, 186, 164, 72, 108, 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