Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfad45455d6ff055182356fb33f11cf3fb9e9a77b7a9529a2d355ce64615a3fa

Tx prefix hash: 282fba78ac59b4148508b11e6c7216c8cbb85e7c1b39472d8bca4f1cb2aec855
Tx public key: a54fd35c19fa680615d8d338cc5de1a50dff58a1fe5f1f1419eee72744360e69
Timestamp: 1702089298 Timestamp [UCT]: 2023-12-09 02:34:58 Age [y:d:h:m:s]: 01:040:11:01:10
Block: 909058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290288 RingCT/type: yes/0
Extra: 01a54fd35c19fa680615d8d338cc5de1a50dff58a1fe5f1f1419eee72744360e69021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c1767de76f68b55fefdd0bbcdb4a3ed4b543db7fc9b4061836c134c5744d32 0.600000000000 1366123 of 15

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": 909068, "vin": [ { "gen": { "height": 909058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c1767de76f68b55fefdd0bbcdb4a3ed4b543db7fc9b4061836c134c5744d32" } } ], "extra": [ 1, 165, 79, 211, 92, 25, 250, 104, 6, 21, 216, 211, 56, 204, 93, 225, 165, 13, 255, 88, 161, 254, 95, 31, 20, 25, 238, 231, 39, 68, 54, 14, 105, 2, 17, 0, 0, 0, 2, 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