Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8dd5205527c8a67537a1a4141e4c5a2d060695feb594fb12337ea9d0a389b18

Tx prefix hash: 4ea4246f649c6c536c54a606e42e0aa06e1e0888987e293767f882b0abc4b5c0
Tx public key: c17b7f5eea50f99ef354a3e7e84984a7f181c5dd3f7178b50fe59d7e2cadf4ae
Timestamp: 1729498681 Timestamp [UCT]: 2024-10-21 08:18:01 Age [y:d:h:m:s]: 00:208:12:43:05
Block: 1136263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148870 RingCT/type: yes/0
Extra: 01c17b7f5eea50f99ef354a3e7e84984a7f181c5dd3f7178b50fe59d7e2cadf4ae021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa871b5b0754e7431e55bc5534ac3e76672219d0710f847cb6c97a554a30d2c7 0.600000000000 1619608 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": 1136273, "vin": [ { "gen": { "height": 1136263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa871b5b0754e7431e55bc5534ac3e76672219d0710f847cb6c97a554a30d2c7" } } ], "extra": [ 1, 193, 123, 127, 94, 234, 80, 249, 158, 243, 84, 163, 231, 232, 73, 132, 167, 241, 129, 197, 221, 63, 113, 120, 181, 15, 229, 157, 126, 44, 173, 244, 174, 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