Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be31da90e8056e6725fa86b93e6b759095ac9c9c062fbd2d9f736c48eb4ff48a

Tx prefix hash: b09c81e2cd2c166cbffd5fbc3b529cc9cac66edd1b37254f13c41ef6ac61d7b3
Tx public key: 66d6111deb7e0be01c63b2bc2e59bb7a4ad0cd1a2eb670c3f9f929a3e8d1fad1
Timestamp: 1649911633 Timestamp [UCT]: 2022-04-14 04:47:13 Age [y:d:h:m:s]: 02:340:05:57:14
Block: 479790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762861 RingCT/type: yes/0
Extra: 0166d6111deb7e0be01c63b2bc2e59bb7a4ad0cd1a2eb670c3f9f929a3e8d1fad1021100000001a8c141c5000000000000000000

1 output(s) for total of 15.785633743000 dcy

stealth address amount amount idx
00: 8026068a864228b09e88ce1161e89db227ba4ea47b42818f9ab28b6ebf8c5c06 15.785633743000 900753 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": 479800, "vin": [ { "gen": { "height": 479790 } } ], "vout": [ { "amount": 15785633743, "target": { "key": "8026068a864228b09e88ce1161e89db227ba4ea47b42818f9ab28b6ebf8c5c06" } } ], "extra": [ 1, 102, 214, 17, 29, 235, 126, 11, 224, 28, 99, 178, 188, 46, 89, 187, 122, 74, 208, 205, 26, 46, 182, 112, 195, 249, 249, 41, 163, 232, 209, 250, 209, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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