Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ba118dd5c596d886ddcb5c2bb3c4a83652ced856b18c60639e08ec6de82cf9

Tx prefix hash: 3e0e3f36574e37d9695e3af77c2286e90b8af95a4f74b77c294ea778ac245100
Tx public key: 792abc2152192a58a172559513fa45d9f19ef355210a8b008435f2cee3ecb291
Timestamp: 1714618842 Timestamp [UCT]: 2024-05-02 03:00:42 Age [y:d:h:m:s]: 00:337:08:30:14
Block: 1012943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241150 RingCT/type: yes/0
Extra: 01792abc2152192a58a172559513fa45d9f19ef355210a8b008435f2cee3ecb2910211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 303cb524b00838690bcffc70a5f13f41a1449d9ddc6a614ebf10cb7e0aa0a8bb 0.600000000000 1475622 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": 1012953, "vin": [ { "gen": { "height": 1012943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "303cb524b00838690bcffc70a5f13f41a1449d9ddc6a614ebf10cb7e0aa0a8bb" } } ], "extra": [ 1, 121, 42, 188, 33, 82, 25, 42, 88, 161, 114, 85, 149, 19, 250, 69, 217, 241, 158, 243, 85, 33, 10, 139, 0, 132, 53, 242, 206, 227, 236, 178, 145, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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