Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4f6a013c938f850e0f73fb4f32551f035fbd83811c1f674c6ccface4fb61fe

Tx prefix hash: 369df3f594a00f2f8acdad17dd3b133c0e154972b5005a0f1e2c0df6a2fd9330
Tx public key: f37dde4cae72048b76bfcaa4b6ebd89f5164cb4ced4012c4d2fb817ab89f50b7
Timestamp: 1696734816 Timestamp [UCT]: 2023-10-08 03:13:36 Age [y:d:h:m:s]: 01:093:15:52:40
Block: 864884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328190 RingCT/type: yes/0
Extra: 01f37dde4cae72048b76bfcaa4b6ebd89f5164cb4ced4012c4d2fb817ab89f50b7021100000004faf35c9c000000000000000000

1 output(s) for total of 0.836142527000 dcy

stealth address amount amount idx
00: 9965109028e8e81e9eab6fcb136aa4609bbc8c5b421383722833ed2c005659d1 0.836142527000 1319406 of 0

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": 864894, "vin": [ { "gen": { "height": 864884 } } ], "vout": [ { "amount": 836142527, "target": { "key": "9965109028e8e81e9eab6fcb136aa4609bbc8c5b421383722833ed2c005659d1" } } ], "extra": [ 1, 243, 125, 222, 76, 174, 114, 4, 139, 118, 191, 202, 164, 182, 235, 216, 159, 81, 100, 203, 76, 237, 64, 18, 196, 210, 251, 129, 122, 184, 159, 80, 183, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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