Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be767ace2abecdbe9cbaf2d1af329915bd9f17f0fa0f63b03ff9dff3f15c7316

Tx prefix hash: 225471abb94e5601f030ccdd4f0d6f9105437d1c471b46a0cdb300d3879fa530
Tx public key: f50c7fbdfbef6510c795c6010bce7df272fe1a6fd8ef32a6504e6059f4f9beea
Timestamp: 1574497616 Timestamp [UCT]: 2019-11-23 08:26:56 Age [y:d:h:m:s]: 05:170:18:43:13
Block: 15291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1265021 RingCT/type: yes/0
Extra: 01f50c7fbdfbef6510c795c6010bce7df272fe1a6fd8ef32a6504e6059f4f9beea021100000003b63f0b49000000000000000000

1 output(s) for total of 546.179572430000 dcy

stealth address amount amount idx
00: d336045364a6b8aa6f4a43ef35ccb86d4d6ac3d02c6717cdee94038d2f844d4e 546.179572430000 20339 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": 15301, "vin": [ { "gen": { "height": 15291 } } ], "vout": [ { "amount": 546179572430, "target": { "key": "d336045364a6b8aa6f4a43ef35ccb86d4d6ac3d02c6717cdee94038d2f844d4e" } } ], "extra": [ 1, 245, 12, 127, 189, 251, 239, 101, 16, 199, 149, 198, 1, 11, 206, 125, 242, 114, 254, 26, 111, 216, 239, 50, 166, 80, 78, 96, 89, 244, 249, 190, 234, 2, 17, 0, 0, 0, 3, 182, 63, 11, 73, 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