Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb103ce1dfdcd4b75c71ecdc09c097e7c876e80172836d25d64d33c5f7dcf8c

Tx prefix hash: f2099b86d5fa76d071db23a1c66ae6718d99da974d7ff345cbf1bb57eb62d27b
Tx public key: 1e9f28d51f719a5c913faee9a8232ef25419142b3b8477c255e4708513c30765
Timestamp: 1627561820 Timestamp [UCT]: 2021-07-29 12:30:20 Age [y:d:h:m:s]: 03:194:11:28:47
Block: 303154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911264 RingCT/type: yes/0
Extra: 011e9f28d51f719a5c913faee9a8232ef25419142b3b8477c255e4708513c3076502110000001617696b73000000000000000000

1 output(s) for total of 60.747084423000 dcy

stealth address amount amount idx
00: 359ae4ef805e436f3a1b0f4e9f80d9100d2de89a37e3026d4fea6c3bb6db86cb 60.747084423000 632769 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": 303164, "vin": [ { "gen": { "height": 303154 } } ], "vout": [ { "amount": 60747084423, "target": { "key": "359ae4ef805e436f3a1b0f4e9f80d9100d2de89a37e3026d4fea6c3bb6db86cb" } } ], "extra": [ 1, 30, 159, 40, 213, 31, 113, 154, 92, 145, 63, 174, 233, 168, 35, 46, 242, 84, 25, 20, 43, 59, 132, 119, 194, 85, 228, 112, 133, 19, 195, 7, 101, 2, 17, 0, 0, 0, 22, 23, 105, 107, 115, 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