Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a24e85a03ee2d112e14654c4a93343149a2d3d8f2b133fb9c94188b5dc348d

Tx prefix hash: 1db7758e4782b763f908ee9024ab4adfe86702ecd2c62e80d60a096bfc548f0e
Tx public key: 4dbabf6cb40fbdd59846e895fdace92f6fa91f3c7baca95d199773eae419acfd
Timestamp: 1590431466 Timestamp [UCT]: 2020-05-25 18:31:06 Age [y:d:h:m:s]: 04:216:20:52:26
Block: 103151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081225 RingCT/type: yes/0
Extra: 014dbabf6cb40fbdd59846e895fdace92f6fa91f3c7baca95d199773eae419acfd02110000009325a1e897000000000000000000

1 output(s) for total of 279.412159119000 dcy

stealth address amount amount idx
00: b093ae5a1d7790e05816336fdf5aea909184a6e18dcb92e1962f06e43130df8a 279.412159119000 181026 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": 103161, "vin": [ { "gen": { "height": 103151 } } ], "vout": [ { "amount": 279412159119, "target": { "key": "b093ae5a1d7790e05816336fdf5aea909184a6e18dcb92e1962f06e43130df8a" } } ], "extra": [ 1, 77, 186, 191, 108, 180, 15, 189, 213, 152, 70, 232, 149, 253, 172, 233, 47, 111, 169, 31, 60, 123, 172, 169, 93, 25, 151, 115, 234, 228, 25, 172, 253, 2, 17, 0, 0, 0, 147, 37, 161, 232, 151, 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