Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50084b42530e64402067c4f60c37f86c0531c61773760d6fcb5bb594d3642f5e

Tx prefix hash: 70486a8e9eee79e8d637b42234476771a0a847588e0a06158b62926c2529d60b
Tx public key: 9f7b684ccf6b7f105c81d0420e095d3348d53f7eed276d15900e4a6a7c9649c4
Timestamp: 1673406267 Timestamp [UCT]: 2023-01-11 03:04:27 Age [y:d:h:m:s]: 02:141:16:59:50
Block: 672129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623005 RingCT/type: yes/0
Extra: 019f7b684ccf6b7f105c81d0420e095d3348d53f7eed276d15900e4a6a7c9649c40211000000028b7b6602000000000000000000

1 output(s) for total of 3.638794781000 dcy

stealth address amount amount idx
00: eb5ece4e40fc87f0174be2b4316254b19e477b4767564b290b232a684f800807 3.638794781000 1113644 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": 672139, "vin": [ { "gen": { "height": 672129 } } ], "vout": [ { "amount": 3638794781, "target": { "key": "eb5ece4e40fc87f0174be2b4316254b19e477b4767564b290b232a684f800807" } } ], "extra": [ 1, 159, 123, 104, 76, 207, 107, 127, 16, 92, 129, 208, 66, 14, 9, 93, 51, 72, 213, 63, 126, 237, 39, 109, 21, 144, 14, 74, 106, 124, 150, 73, 196, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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