Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1cf3e4fd0205b9d7dcfa4ac9d74f039a074da6257c2ba8e13915b056612d813

Tx prefix hash: 6c29d87d4e81d9a66ba7c2bf5e5f2a1651099de59a5b020740efd2aceabf4e55
Tx public key: 94f05d95b4c7fa31a4ebbc77bc5c8a503609e3a777a83a9b360b08c0a52dc441
Timestamp: 1696084341 Timestamp [UCT]: 2023-09-30 14:32:21 Age [y:d:h:m:s]: 01:217:21:16:36
Block: 859486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416792 RingCT/type: yes/0
Extra: 0194f05d95b4c7fa31a4ebbc77bc5c8a503609e3a777a83a9b360b08c0a52dc44102110000000e4b8f5122000000000000000000

1 output(s) for total of 0.871296832000 dcy

stealth address amount amount idx
00: ee8e26acf2018f76573d9bad0f967a726b537e589ebf8305d8c6f96a51bf8e88 0.871296832000 1313714 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": 859496, "vin": [ { "gen": { "height": 859486 } } ], "vout": [ { "amount": 871296832, "target": { "key": "ee8e26acf2018f76573d9bad0f967a726b537e589ebf8305d8c6f96a51bf8e88" } } ], "extra": [ 1, 148, 240, 93, 149, 180, 199, 250, 49, 164, 235, 188, 119, 188, 92, 138, 80, 54, 9, 227, 167, 119, 168, 58, 155, 54, 11, 8, 192, 165, 45, 196, 65, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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