Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91177b95e1ad7b93f8944b98fcef811b158fc66f55296036eacf49cb253d6402

Tx prefix hash: cf6e96fe82906402c0f8b65061e28b789ce4f8e25d4e1faecbc36cb970b6593e
Tx public key: ca9256b70b4c6294ea91287eedb2a7b1799e841406329e46a36e9ce5c6d6be33
Timestamp: 1722403662 Timestamp [UCT]: 2024-07-31 05:27:42 Age [y:d:h:m:s]: 00:278:06:35:50
Block: 1077480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198807 RingCT/type: yes/0
Extra: 01ca9256b70b4c6294ea91287eedb2a7b1799e841406329e46a36e9ce5c6d6be33021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb2306a4537f44b7d8b553069f5534f7b51167eb612f9ff1bfc5664bd3660a1 0.600000000000 1550029 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": 1077490, "vin": [ { "gen": { "height": 1077480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb2306a4537f44b7d8b553069f5534f7b51167eb612f9ff1bfc5664bd3660a1" } } ], "extra": [ 1, 202, 146, 86, 183, 11, 76, 98, 148, 234, 145, 40, 126, 237, 178, 167, 177, 121, 158, 132, 20, 6, 50, 158, 70, 163, 110, 156, 229, 198, 214, 190, 51, 2, 17, 0, 0, 0, 9, 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