Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c0f8c7ee75909dbcca9112ae1c2a7be5ab43dd86d57cb1fb546e830337bb42

Tx prefix hash: ae8ed73da9cac8a88f5a61efab1c42d23c6b7b7ab9084686998e37bd93da59db
Tx public key: 79d351903b8a94093fd5fc82612ca4e4f790aaa7199e5d3eeda69cdb53ea5238
Timestamp: 1736529732 Timestamp [UCT]: 2025-01-10 17:22:12 Age [y:d:h:m:s]: 00:104:11:29:52
Block: 1194460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74460 RingCT/type: yes/0
Extra: 0179d351903b8a94093fd5fc82612ca4e4f790aaa7199e5d3eeda69cdb53ea52380211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dc45a791031391c6d4aac7b47d2e13bfd19fe2599ef94a5bcf66bfc852951db 0.600000000000 1681031 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": 1194470, "vin": [ { "gen": { "height": 1194460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dc45a791031391c6d4aac7b47d2e13bfd19fe2599ef94a5bcf66bfc852951db" } } ], "extra": [ 1, 121, 211, 81, 144, 59, 138, 148, 9, 63, 213, 252, 130, 97, 44, 164, 228, 247, 144, 170, 167, 25, 158, 93, 62, 237, 166, 156, 219, 83, 234, 82, 56, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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