Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539362f54635bbee3af8c81f52157616f2e29df7adb21d2e68c4839d2606bf73

Tx prefix hash: 039ba14d5b9047136219c09b54b0fb235abdc059a82240015d3314500e5780d2
Tx public key: e161d485cbae620fdb4906c6d146bb1f8b6b2bbaf37cec401a23f8f186f1682f
Timestamp: 1725649050 Timestamp [UCT]: 2024-09-06 18:57:30 Age [y:d:h:m:s]: 00:235:02:15:23
Block: 1104393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167882 RingCT/type: yes/0
Extra: 01e161d485cbae620fdb4906c6d146bb1f8b6b2bbaf37cec401a23f8f186f1682f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 772a830215cb024ba1981bc5eb65230d396a80f8bb45b953f94971220230e15d 0.600000000000 1581514 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": 1104403, "vin": [ { "gen": { "height": 1104393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "772a830215cb024ba1981bc5eb65230d396a80f8bb45b953f94971220230e15d" } } ], "extra": [ 1, 225, 97, 212, 133, 203, 174, 98, 15, 219, 73, 6, 198, 209, 70, 187, 31, 139, 107, 43, 186, 243, 124, 236, 64, 26, 35, 248, 241, 134, 241, 104, 47, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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