Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d11d11c15c74731af30e64b97220aea1c00f58c069b4486a522484b8898ed88c

Tx prefix hash: 8b861610a432a51251ef4e45bda7fb75d2233c04216d8149e00e9abb4d297d0e
Tx public key: 3791d0a4e52ff718d986e6df9e6ef2e578a3e01db20f06c0c8af9c4520356ea9
Timestamp: 1718853934 Timestamp [UCT]: 2024-06-20 03:25:34 Age [y:d:h:m:s]: 00:284:03:54:26
Block: 1048058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203047 RingCT/type: yes/0
Extra: 013791d0a4e52ff718d986e6df9e6ef2e578a3e01db20f06c0c8af9c4520356ea902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8e8ac524a5ef68ffaa9c1b9a76b4ac75e6b5cd6367ab5586e84ae620ca1840d 0.600000000000 1518041 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": 1048068, "vin": [ { "gen": { "height": 1048058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8e8ac524a5ef68ffaa9c1b9a76b4ac75e6b5cd6367ab5586e84ae620ca1840d" } } ], "extra": [ 1, 55, 145, 208, 164, 229, 47, 247, 24, 217, 134, 230, 223, 158, 110, 242, 229, 120, 163, 224, 29, 178, 15, 6, 192, 200, 175, 156, 69, 32, 53, 110, 169, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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