Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e891e4d2cf8e0cfadd2d4579bc68b6615a433292ba5a3834f18840a9ad5334

Tx prefix hash: e428559676bad1379733e1d70f560b4c2bf8c19db7290840e1a1307835e332be
Tx public key: f9f38eb9c7b08b8620c612f267ae301a0474fbbc67f29048bd4e765400fa3d21
Timestamp: 1700443222 Timestamp [UCT]: 2023-11-20 01:20:22 Age [y:d:h:m:s]: 01:064:03:41:08
Block: 895420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307204 RingCT/type: yes/0
Extra: 01f9f38eb9c7b08b8620c612f267ae301a0474fbbc67f29048bd4e765400fa3d21021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.662371783000 dcy

stealth address amount amount idx
00: b7f33091378aee3408fcacb18c5114ba7edc7e08e8dd01dc826bcbe8bed44a1a 0.662371783000 1351657 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": 895430, "vin": [ { "gen": { "height": 895420 } } ], "vout": [ { "amount": 662371783, "target": { "key": "b7f33091378aee3408fcacb18c5114ba7edc7e08e8dd01dc826bcbe8bed44a1a" } } ], "extra": [ 1, 249, 243, 142, 185, 199, 176, 139, 134, 32, 198, 18, 242, 103, 174, 48, 26, 4, 116, 251, 188, 103, 242, 144, 72, 189, 78, 118, 84, 0, 250, 61, 33, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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