Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9e74686ce40e77865540f5d71744f67017b7901e841286a1d2114a2d2d2784

Tx prefix hash: d357a29959a073bc12d600ba8c2af4b1f2f90800a343f8c957e1fcdf8f7e10a0
Tx public key: 1d7254c7e7cdd5311af34ef8f9cf4c243a0688e5c930543097b16892ed6b4d60
Timestamp: 1576427334 Timestamp [UCT]: 2019-12-15 16:28:54 Age [y:d:h:m:s]: 05:021:07:47:58
Block: 27799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161862 RingCT/type: yes/0
Extra: 011d7254c7e7cdd5311af34ef8f9cf4c243a0688e5c930543097b16892ed6b4d6002110000001aad433a0b000000000000000000

1 output(s) for total of 496.467974220000 dcy

stealth address amount amount idx
00: 4d356beab32f4fb0f6c585aadf0db69623d1d26aa4e28c9cc9a2c72f0a89160e 496.467974220000 45853 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": 27809, "vin": [ { "gen": { "height": 27799 } } ], "vout": [ { "amount": 496467974220, "target": { "key": "4d356beab32f4fb0f6c585aadf0db69623d1d26aa4e28c9cc9a2c72f0a89160e" } } ], "extra": [ 1, 29, 114, 84, 199, 231, 205, 213, 49, 26, 243, 78, 248, 249, 207, 76, 36, 58, 6, 136, 229, 201, 48, 84, 48, 151, 177, 104, 146, 237, 107, 77, 96, 2, 17, 0, 0, 0, 26, 173, 67, 58, 11, 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