Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7faa2a2513f499115862a54e22758f1fd23607b84ef3a317ebfe213656f75044

Tx prefix hash: e4529e417ac3577ad212a7296fce8a5d69a938b97ae1f93162614c1fa9f9fefe
Tx public key: f382759cbb9ec6837b063b00387063f779f8adc014e74059b0304f7ee4e3a1b3
Timestamp: 1733664184 Timestamp [UCT]: 2024-12-08 13:23:04 Age [y:d:h:m:s]: 00:126:13:25:25
Block: 1170744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90262 RingCT/type: yes/0
Extra: 01f382759cbb9ec6837b063b00387063f779f8adc014e74059b0304f7ee4e3a1b3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c5113a9d32b84563ee7cf130d65cca21c68d64486bcd06bdce53ad84b05d7d 0.600000000000 1656477 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": 1170754, "vin": [ { "gen": { "height": 1170744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c5113a9d32b84563ee7cf130d65cca21c68d64486bcd06bdce53ad84b05d7d" } } ], "extra": [ 1, 243, 130, 117, 156, 187, 158, 198, 131, 123, 6, 59, 0, 56, 112, 99, 247, 121, 248, 173, 192, 20, 231, 64, 89, 176, 48, 79, 126, 228, 227, 161, 179, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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