Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14844ba6545b437ff73083160dadc66bf8057c56e714f66a5eb3f016d7ea40ca

Tx prefix hash: 11017c131ef74776e010081ad29a823d5f15201d79a6326cf36ed7f7f3566adf
Tx public key: f70baa2a21192a0f129f756cb877d5ed243723a84998e982bddc5ae74de5f8ac
Timestamp: 1700957960 Timestamp [UCT]: 2023-11-26 00:19:20 Age [y:d:h:m:s]: 01:158:16:16:42
Block: 899678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374593 RingCT/type: yes/0
Extra: 01f70baa2a21192a0f129f756cb877d5ed243723a84998e982bddc5ae74de5f8ac021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.641199678000 dcy

stealth address amount amount idx
00: 585dda6e24858aa34ea91ff9bf2e590d89bcf50e217fd6feac7f8ff63216ec67 0.641199678000 1356141 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": 899688, "vin": [ { "gen": { "height": 899678 } } ], "vout": [ { "amount": 641199678, "target": { "key": "585dda6e24858aa34ea91ff9bf2e590d89bcf50e217fd6feac7f8ff63216ec67" } } ], "extra": [ 1, 247, 11, 170, 42, 33, 25, 42, 15, 18, 159, 117, 108, 184, 119, 213, 237, 36, 55, 35, 168, 73, 152, 233, 130, 189, 220, 90, 231, 77, 229, 248, 172, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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