Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12d42ddc053e023ca4415fea2951155dc27473c620c856548d1099fc3169dfcd

Tx prefix hash: 9c802e629c3c245d4c3b600b7aa79bd6a8b98d16ebe0225c4d7de66c27d0f48b
Tx public key: f52a25b1de1ad87a3b3215ec54cf27af6440af7484fdbf47c769a42e75ca6b52
Timestamp: 1661573084 Timestamp [UCT]: 2022-08-27 04:04:44 Age [y:d:h:m:s]: 02:208:01:51:21
Block: 574670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669961 RingCT/type: yes/0
Extra: 01f52a25b1de1ad87a3b3215ec54cf27af6440af7484fdbf47c769a42e75ca6b52021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.653847931000 dcy

stealth address amount amount idx
00: 1a47c147d621a6f0abc3e7a5757e17d94f4a9c4df374f97e44558a95d8e1081c 7.653847931000 1007990 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": 574680, "vin": [ { "gen": { "height": 574670 } } ], "vout": [ { "amount": 7653847931, "target": { "key": "1a47c147d621a6f0abc3e7a5757e17d94f4a9c4df374f97e44558a95d8e1081c" } } ], "extra": [ 1, 245, 42, 37, 177, 222, 26, 216, 122, 59, 50, 21, 236, 84, 207, 39, 175, 100, 64, 175, 116, 132, 253, 191, 71, 199, 105, 164, 46, 117, 202, 107, 82, 2, 17, 0, 0, 0, 1, 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