Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccedff1a209fcf8ab499ddf306704782d746ba92320c9af4c935763dfe87cdb8

Tx prefix hash: 3372801137071cc3ae08655f7632d82e132b4dfc1c20eae56d923f2898849801
Tx public key: 3e7e27845a2123ec7a05e1f6b46c47b47b958c4bdae37c746d79d6ff1d36a6c5
Timestamp: 1577841617 Timestamp [UCT]: 2020-01-01 01:20:17 Age [y:d:h:m:s]: 05:099:18:48:43
Block: 36083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221123 RingCT/type: yes/0
Extra: 013e7e27845a2123ec7a05e1f6b46c47b47b958c4bdae37c746d79d6ff1d36a6c50211000000094ac5aa02000000000000000000

1 output(s) for total of 466.061142654000 dcy

stealth address amount amount idx
00: 838dcc6efaf007d996613cc521e527993356e8d7c8ea3619904c7a39d73df1df 466.061142654000 61002 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": 36093, "vin": [ { "gen": { "height": 36083 } } ], "vout": [ { "amount": 466061142654, "target": { "key": "838dcc6efaf007d996613cc521e527993356e8d7c8ea3619904c7a39d73df1df" } } ], "extra": [ 1, 62, 126, 39, 132, 90, 33, 35, 236, 122, 5, 225, 246, 180, 108, 71, 180, 123, 149, 140, 75, 218, 227, 124, 116, 109, 121, 214, 255, 29, 54, 166, 197, 2, 17, 0, 0, 0, 9, 74, 197, 170, 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