Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede755df6cf59a100fbc53558b4d82d44066990b702ca22e3ba36c74e5b7e363

Tx prefix hash: ffc92a4d035a0e8ba597f50a97dddf6763fee63ea3e6ee115388fc0a273bb936
Tx public key: c05ca77a0ef12c1a04e2c7cecd3da47713744b9cad94c15e97dd432b94dcb443
Timestamp: 1731543273 Timestamp [UCT]: 2024-11-14 00:14:33 Age [y:d:h:m:s]: 00:218:03:01:21
Block: 1153166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155625 RingCT/type: yes/0
Extra: 01c05ca77a0ef12c1a04e2c7cecd3da47713744b9cad94c15e97dd432b94dcb4430211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c9df7e7ad4c2862c643e93e231ab8fef6792c871d883897aa19a18a9c2d101 0.600000000000 1638775 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": 1153176, "vin": [ { "gen": { "height": 1153166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c9df7e7ad4c2862c643e93e231ab8fef6792c871d883897aa19a18a9c2d101" } } ], "extra": [ 1, 192, 92, 167, 122, 14, 241, 44, 26, 4, 226, 199, 206, 205, 61, 164, 119, 19, 116, 75, 156, 173, 148, 193, 94, 151, 221, 67, 43, 148, 220, 180, 67, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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